Debit network routing selection using a scannable code

ABSTRACT

Embodiments are directed to selecting a debit network using a quick response (QR) code and to processing a payment using a debit network selected according to information embedded in a QR code. In one scenario, a mobile computer system receives input indicating that a user has initiated a payment for various items sold by a provider of goods or services. The mobile computer system determines that the user or the provider has specified a preference indicating which debit network is to be used to process the payment. The mobile computer system then generates a QR code with the debit network selection and portions of the user&#39;s debit account information embedded in the QR code, and sends the generated QR code to a payment processing system. The payment processing system may be cloud-based, or may be run locally at the provider&#39;s point of sale.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. ProvisionalApplication Ser. No. 61/704,337, entitled “Debit Network RoutingSelection Using a QR Code”, filed on Sep. 21, 2012. This applicationalso claims priority to and the benefit of U.S. Provisional ApplicationSer. No. 61/693,055, entitled “Debit Network Routing Selection Using aQR Code”, filed on Aug. 24, 2012. Both of these applications areincorporated by reference herein in their entirety.

BACKGROUND

Computers have become highly integrated in the workforce, in the home,in mobile devices, and many other places. Computers can process massiveamounts of information quickly and efficiently. Software applicationsdesigned to run on computer systems allow users to perform a widevariety of functions including business applications, schoolwork,entertainment and more. Software applications are often designed toperform specific tasks, such as word processor applications for draftingdocuments, or email programs for sending, receiving and organizingemail.

Today's smart phones use software applications to perform a wide varietyof functionality. In some cases, this functionality may include theability to pay for items using a mobile payment system. Such a mobilepayment system may allow users to pay for items at a store or over theinternet using their phone.

BRIEF SUMMARY

Embodiments described herein are directed to selecting a debit networkusing a quick response (QR) code and to processing a payment using adebit network selected according to information embedded in a QR code.In one embodiment, a mobile computer system receives input indicatingthat a user has initiated a payment for various items sold by a providerof goods or services. The mobile computer system determines that theuser or the provider has specified a preference indicating which debitnetwork is to be used to process the payment. The mobile computer systemthen generates a QR code with the debit network selection and portionsof the user's debit account information embedded in the QR code, andsends the generated QR code to a payment processing system. The paymentprocessing system may be cloud-based, or may be run locally at theprovider's point of sale.

In another embodiment, a computer system processes a payment using adebit network selected according to information embedded in a QR code.The computer system receives a QR code that includes portions ofembedded payment information. The embedded payment information includesat least the following: a total payment amount that is to be paid by auser, debit account information for the user, and an indication of whichdebit network is to be used to process the payment. The computer systemdetermines which debit network is to be used to process the paymentbased on the indication provided in the embedded payment information inthe received QR code, sends the payment amount and the user's debitaccount information to the determined debit network and, after thepayment has been processed, receives an indication that the payment wasprocessed by the determined debit network.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Additional features and advantages will be set forth in the descriptionwhich follows, and in part will be apparent to one of ordinary skill inthe art from the description, or may be learned by the practice of theteachings herein. Features and advantages of embodiments describedherein may be realized and obtained by means of the instruments andcombinations particularly pointed out in the appended claims. Featuresof the embodiments described herein will become more fully apparent fromthe following description and appended claims.

BRIEF DESCRIPTION OF THE DRAWINGS

To further clarify the above and other features of the embodimentsdescribed herein, a more particular description will be rendered byreference to the appended drawings. It is appreciated that thesedrawings depict only examples of the embodiments described herein andare therefore not to be considered limiting of its scope. Theembodiments will be described and explained with additional specificityand detail through the use of the accompanying drawings in which:

FIG. 1 illustrates a computer platform architecture for providing mobilewallet and payment processing services.

FIG. 2 illustrates an embodiment in which a debit network is selectedfor performing a debit transaction.

FIG. 3 illustrates a flowchart of an example method for selecting adebit network using a QR code.

FIG. 4 illustrates a flowchart of an example method for processing apayment using a debit network selected according to information embeddedin a QR code.

FIG. 5 illustrates a QR code with multiple portions of embeddedinformation.

DETAILED DESCRIPTION

Embodiments described herein are directed to selecting a debit networkusing a quick response (QR) code and to processing a payment using adebit network selected according to information embedded in a QR code.In one embodiment, a mobile computer system receives input indicatingthat a user has initiated a payment for various items sold by a providerof goods or services. The mobile computer system determines that theuser or the provider has specified a preference indicating which debitnetwork is to be used to process the payment. The mobile computer systemthen generates a QR code with the debit network selection and portionsof the user's debit account information embedded in the QR code, andsends the generated QR code to a payment processing system. The paymentprocessing system may be cloud-based, or may be run locally at theprovider's point of sale.

In another embodiment, a computer system processes a payment using adebit network selected according to information embedded in a QR code.The computer system receives a QR code that includes portions ofembedded payment information. The embedded payment information includesat least the following: a total payment amount that is to be paid by auser, debit account information for the user, and an indication of whichdebit network is to be used to process the payment. The computer systemdetermines which debit network is to be used to process the paymentbased on the indication provided in the embedded payment information inthe received QR code, sends the payment amount and the user's debitaccount information to the determined debit network and, after thepayment has been processed, receives an indication that the payment wasprocessed by the determined debit network.

The following discussion now refers to a number of methods and methodacts that may be performed. It should be noted, that although the methodacts may be discussed in a certain order or illustrated in a flow chartas occurring in a particular order, no particular ordering isnecessarily required unless specifically stated, or required because anact is dependent on another act being completed prior to the act beingperformed.

Embodiments of the present invention may comprise or utilize aspecial-purpose or general-purpose computer system that includescomputer hardware, such as, for example, one or more processors andsystem memory, as discussed in greater detail below. Embodiments withinthe scope of the present invention also include physical and othercomputer-readable media for carrying or storing computer-executableinstructions and/or data structures. Such computer-readable media can beany available media that can be accessed by a general-purpose orspecial-purpose computer system. Computer-readable media that storecomputer-executable instructions and/or data structures are computerstorage media. Computer-readable media that carry computer-executableinstructions and/or data structures are transmission media. Thus, by wayof example, and not limitation, embodiments of the invention cancomprise at least two distinctly different kinds of computer-readablemedia: computer storage media and transmission media.

Computer storage media are physical storage media that storecomputer-executable instructions and/or data structures. Physicalstorage media include computer hardware, such as RAM, ROM, EEPROM, solidstate drives (“SSDs”), flash memory, phase-change memory (“PCM”),optical disk storage, magnetic disk storage or other magnetic storagedevices, or any other hardware storage device(s) which can be used tostore program code in the form of computer-executable instructions ordata structures, which can be accessed and executed by a general-purposeor special-purpose computer system to implement the functionalitydisclosed herein.

Transmission media can include a network and/or data links which can beused to carry program code in the form of computer-executableinstructions or data structures, and which can be accessed by ageneral-purpose or special-purpose computer system. A “network” isdefined as one or more data links that enable the transport ofelectronic data between computer systems and/or modules and/or otherelectronic devices. When information is transferred or provided over anetwork or another communications connection (either hardwired,wireless, or a combination of hardwired or wireless) to a computersystem, the computer system may view the connection as transmissionmedia. Combinations of the above should also be included within thescope of computer-readable media.

Further, upon reaching various computer system components, program codein the form of computer-executable instructions or data structures canbe transferred automatically from transmission media to computer storagemedia (or vice versa). For example, computer-executable instructions ordata structures received over a network or data link can be buffered inRAM within a network interface module (e.g., a “NIC”), and theneventually transferred to computer system RAM and/or to less volatilecomputer storage media at a computer system. Thus, it should beunderstood that computer storage media can be included in computersystem components that also (or even primarily) utilize transmissionmedia.

Computer-executable instructions comprise, for example, instructions anddata which, when executed at one or more processors, cause ageneral-purpose computer system, special-purpose computer system, orspecial-purpose processing device to perform a certain function or groupof functions. Computer-executable instructions may be, for example,binaries, intermediate format instructions such as assembly language, oreven source code.

Those skilled in the art will appreciate that the invention may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, tablets, pagers, routers, switches, and the like. The inventionmay also be practiced in distributed system environments where local andremote computer systems, which are linked (either by hardwired datalinks, wireless data links, or by a combination of hardwired andwireless data links) through a network, both perform tasks. As such, ina distributed system environment, a computer system may include aplurality of constituent computer systems. In a distributed systemenvironment, program modules may be located in both local and remotememory storage devices.

In this description and the following claims, “cloud computing” isdefined as a model for enabling on-demand network access to a sharedpool of configurable computing resources (e.g., networks, servers,storage, applications, and services). The definition of “cloudcomputing” is not limited to any of the other numerous advantages thatcan be obtained from such a model when properly deployed.

For instance, cloud computing is currently employed in the marketplaceso as to offer ubiquitous and convenient on-demand access to the sharedpool of configurable computing resources. Furthermore, the shared poolof configurable computing resources can be rapidly provisioned viavirtualization and released with low management effort or serviceprovider interaction, and then scaled accordingly.

A cloud computing model can be composed of various characteristics suchas on-demand self-service, broad network access, resource pooling, rapidelasticity, measured service, and so forth. A cloud computing model mayalso come in the form of various service models such as, for example,Software as a Service (“SaaS”), Platform as a Service (“PaaS”), andInfrastructure as a Service (“IaaS”). The cloud computing model may alsobe deployed using different deployment models such as private cloud,community cloud, public cloud, hybrid cloud, and so forth. In thisdescription and in the claims, a “cloud computing environment” is anenvironment in which cloud computing is employed.

Additionally or alternatively, the functionally described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), and other types of programmablehardware.

Still further, system architectures described herein can include aplurality of independent components that each contribute to thefunctionality of the system as a whole. This modularity allows forincreased flexibility when approaching issues of platform scalabilityand, to this end, provides a variety of advantages. System complexityand growth can be managed more easily through the use of smaller-scaleparts with limited functional scope. Platform fault tolerance isenhanced through the use of these loosely coupled modules. Individualcomponents can be grown incrementally as business needs dictate. Modulardevelopment also translates to decreased time to market for newfunctionality. New functionality can be added or subtracted withoutimpacting the core system.

FIG. 1 illustrates an example system architecture for a mobile walletplatform. Integration tier 101 is configured to manage mobile walletsessions and maintain integrity of financial transactions. Integrationtier 101 can also include a communication (e.g., Web services) APIand/or other communication mechanisms to accept messages from channels111. Other mechanisms include, but are not limited to: InternationalStandards Organization (“ISO”) 8583 for Point of Sale (“POS”) andAutomated Teller Machines (“ATM”) devices and Advanced Message QueuingProtocol (“AMQP”) for queue based interfaces. Each of channels 111 canbe integrated to one or more mechanisms for sending messages tointegration tier 101. Notification services 102 is configured to sendvarious notifications through different notification channels 112, suchas, for example, Short Message Peer-to-Peer (“SSMP”) for Short MessagingService (“SMS”) and Simple Mail Transfer Protocol (“SMTP”) for emails.Notification services 102 can be configured through a web services API.

Service connectors 103 are a set of connectors configure to connect to3rd party systems 113. Each connector can be a separate module intendedto integrate an external service to the system architecture. Businessprocess services 104 are configured to implement business workflows,including executing financial transactions, auditing financialtransactions, invoking third-party services, handling errors, andlogging platform objects. Payment handler 105 is configured to wrap APIsof different payment processors, such as, for example, banking accounts,credit/debit cards or processor 121. Payment handler 105 exposes acommon API to facilitate interactions with many different kinds ofpayment processors.

Security services 106 are configured to perform subscriberauthentication. Authorization services 107 are configured to performclient authorization, such as, for example, using a database-basedAccess Control List (“ACL”) table.

Database 108 is configured to manage customer accounts (e.g., storingcustomer accounts and properties), manage company accounts (e.g.,storing company accounts and properties), manage transaction histories(e.g., storing financial transaction details), store customer profiles,storing dictionaries used by the mobile wallet platform, such as, forexample, countries, currencies, etc., and managing money containers.Rules engine 109 is configured to gather financial transactionstatistics and uses the statistics to provide transaction properties,such as, for example, fees and bonuses. Rules engine 109 is alsoconfigured to enforce business constraints, such as, for example,transactions and platform license constraints.

Name matching engine 110 is configured to match different objectsaccording to specified configuration rules. Matching engine 110 can beused to find similarities between names, addresses, etc. Transactionprocessor 121 is configured to manage financial accounts andtransactions. The transaction processor 121 can be used to hold, load,withdraw and deposit funds to mobile wallet accounts. Transactionprocessor 121 can also be used as a common interface to a third partyprocessor system. When used as a common interface, financial operationsmay be delegated to the external processor. A Clearing House subsystemof transaction processor 121 can be used to exchange the financialinformation with a bank.

Components of a mobile wallet platform can be connected to one anotherover (or be part of) a system bus and/or a network. Networks can includea Local Area Network (“LAN”), a Wide Area Network (“WAN”), and even theInternet. Accordingly, components of the mobile wallet platform can be“in the cloud”. As such, mobile wallet platform components as well asany other connected computer systems and their components, can createmessage related data and exchange message related data (e.g., InternetProtocol (“IP”) datagrams and other higher layer protocols that utilizeIP datagrams, such as, Transmission Control Protocol (“TCP”), HypertextTransfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”),etc.) over the system bus and/or network.

The components depicted in FIG. 1 can interoperate to provide a numberof financial and other services including but not limited to enrolling acustomer for a mobile wallet, adding a stored value account (eitherhosted by a mobile wallet platform or a third party), adding a bank orcredit union account to a mobile wallet, adding a debit or credit cardaccount to a mobile wallet, depositing funds in a mobile wallet,withdrawing funds from a mobile wallet, paying bills from a mobilewallet, topping up a prepaid mobile account through a mobile wallet,transferring funds through a mobile wallet (nationally orinternationally), making in-store purchases using a mobile wallet, andvarious other tasks as described herein below.

The telephone, smartphone, tablet or other computing system thatinteracts with the mobile payment system typically includes a camera,image sensor, image scanner or other hardware that allows a user to scanor capture an image. For instance, as shown in environment 200 of FIG.2, computer system 201 may include a camera 202. The computer system 201may include a telephone, smartphone, tablet or other type of mobilecomputing system. The user of the phone 201 (i.e. user/customer 205) maythus point the camera 202 or other hardware at an object such as a canof soup and either take a picture of the object, or allow software toscan the image using the camera. Software on the phone or tablet 201then performs a local search or consults a database (e.g. over theinternet) to retrieve information related to that item or productincluding coupons or price discounts.

In addition to receiving product information and discounts, the user 205may also use their phone 201 or other device to pay for the items theywish to buy. In one embodiment, a customer may be at a retail location225 shopping for various items 228. Once the customer 205 has finishedshopping, he or she proceeds to the checkout area. The checkout areaincludes a point of sale 226 with a checkout register 227 that typicallyaccepts cash, debit or credit cards as payment. The checkout register227 may also be configured to allow users to pay using a mobile wallet.Accordingly, the customer may use a mobile wallet application 210 on asmartphone (e.g. 201), tablet or other computer system to pay for theitems.

When paying for the items 228, the determining module 215 of user'sdigital device 201 may determine that the user 205 is attempting to usetheir mobile wallet application 210 to pay for the items. The mobilewallet application may use various types of information to determinewhich debit network (e.g. 230A or 230B) is to be used to process thepayment transaction. As will be understood by one skilled in the art,various different debit networks exist for processing debit transactions(e.g. Star or Nice). These debit networks conduct the transactionsbetween the retailer's bank and the customer's bank that allow the userto pay for items using a debit card linked to their own checking (orother type of) account. These debit networks typically charge differentfee amounts for each transaction, and typically receive at least aportion of that fee as income. Debit networks are thus incentivized toprocess an increased number of transactions and provide debittransaction services for a lower price than their competitors.Similarly, retailers are incentivized to select debit networks thatprocess debit transactions for a lower amount. Allowing the user and/orthe retailer to specify a certain debit network for processing debittransactions may lead to an increased number of users for a givennetwork, and may lead to reduced transaction fees for retailers.

As will further be understood by one skilled in the art, debittransactions may be transactions that are processed by traditionalElectronic Funds Transfer (EFT) debit networks (e.g Star, NYCE, PULSE,etc.), but they may alternatively be transactions that are processed viadirect automated clearing house (ACH) debits. In such cases, the debittransactions would be sent to an Originating Depository FinancialInstitution (ODFI). A user may need to provide additional informationabout their bank (in addition to their debit account information) thatwould allow the ACH transaction to be routed through the ODFI, asopposed to using the traditional debit networks. As such, it will beunderstood that when describing debit transactions herein, the debittransactions may be processed by either a traditional debit network, orvia an ACH debit that uses an ODFI to process the transaction.

In some cases, the decision as to which debit network to use for a giventransaction will be based on either the customer's demographicinformation, the customer's payment preferences or the customer'spurchasing history. For example, the user 205 may provide demographicinformation 211 to the mobile wallet application 210 indicating theirage or age range, income or income range, general housing location (e.g.area code) or other similar information. This information may be used,at least in some cases, to provide targeted advertisements, promotionsor coupons to the user via the mobile wallet. The user's demographicinformation 211 may provide indications or other clues that the user mayprefer one debit network over another (e.g. for cost reasons,convenience reasons, or because the user is receiving a discount orreward 231 from a particular debit network). Accordingly, thisinformation may be used by determining module 215 when determining whichdebit network to use for a given transaction.

Similarly, user payment preferences 212 and/or user purchasing history213 for user 205 may be used to determine which debit network to use fora debit transaction. For example, if the user has indicated in theirpayment preferences which debit network to use, that information may beprovided to the determining module 215. Moreover, if the user'spurchasing history indicates that a specified debit network has beenused in all or most of the user's debit transactions, that informationcould also be used by the determining module 215 when making itsdecision as to which debit network to use. The decision as to whichdebit network to use may be based on any of the following: the user'sdemographic information 211, the user's payment preferences 212, theuser's purchasing history 213, or a combination thereof.

Still further, other factors may be taken into account when determiningwhich debit network to use. For instance, the decision may also be basedon the retailer's preferences. For example, different retailers mayprefer to use certain debit networks due to various factors includingpricing (e.g. price per debit transaction). Thus, retail location 225may prefer to use debit network 230A (e.g. Star) over debit network 230Bbecause debit network 230A charges less per debit transaction. Or, theretail location may specify that they prefer to use different debitnetworks at different times of the day, or may specify that they preferto use different debit networks at their East Coast and West Coastbranches. Accordingly, a retailer may specify preferences that varybased on different factors. In some embodiments, these preferences 214may be broadcast to users' mobile wallet applications while they areshopping at the store.

Thus, in this manner, based on customer information (e.g. 211-213)and/or the retailer's preferences 214, the user's mobile walletapplication 210 may determine which debit network is to be used to routethe user's transaction. Once it has been determined which debit networkis going to be used, a QR code 221 may be generated by module 220 withthe debit network selection embedded therein. This QR code 221 may thenbe presented to the retailer 225 when making the purchase. The QR codehas each of the necessary transaction details embedded therein, and alsoindicates on which debit network the transaction is to take place. Insome cases, the QR code may link directly to the selected debit network(as indicated by the dotted arrow lines to debit networks 230A and230B). In such cases, the user may route their payment for merchandisedirectly to the debit network using their mobile wallet.

The QR code 221 is a secure, tokenized QR code that fully represents thedetails of the user's purchase, along with an indication of which debitnetwork has been specified for that transaction. This QR code isscannable by the checkout register 227 and, as a result of the scan,provides a debit network selection (e.g. debit network 230A, 230B orsome other debit network) through which the transaction is to beprocessed.

The debit network selection may be determined dynamically for eachcustomer. Thus, each customer may use a different debit network toprocess their transactions. Moreover, the debit network selection may bedetermined dynamically for each retailer. Thus, as with customers, eachretailer may specify a certain debit network that is to be used whendebit transactions are processed. In some cases, the retailer'spreference for debit network may take precedence over the user'spreferences or buying history. The debit network selection may also bechosen based on the location (e.g. 225) at which the payment isinitiated. For instance, if the customer 205 is purchasing an item in astore on the West Coast, debit network 230A may be used, while if theuser is purchasing an item from a store located on the East Coast, debitnetwork 230B may be used. Still further, different debit networks may beused based on the time of day at which the payment is initiated, basedon the per-transaction costs, based on initiation or other fees or basedon any other criteria established by the retailer or by the user. Theseconcepts will be explained further below with regard to methods 300 and400 of FIGS. 3 and 4, respectively.

In view of the systems and architectures described above, methodologiesthat may be implemented in accordance with the disclosed subject matterwill be better appreciated with reference to the flow charts of FIGS. 3and 4. For purposes of simplicity of explanation, the methodologies areshown and described as a series of blocks. However, it should beunderstood and appreciated that the claimed subject matter is notlimited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methodologies described hereinafter.

FIG. 3 illustrates a flowchart of a method 300 for selecting a debitnetwork using a QR code. The method 300 will now be described withfrequent reference to the components and data of environment 200 of FIG.2.

In Method 300, a mobile computer system receives input indicating that auser has initiated a payment for one or more items sold by a provider ofgoods or services (310). The mobile computer system 201 may be acellular telephone, a tablet, a smartphone, a netbook, a laptop or anyother type of mobile computing system. The mobile computer system mayreceive the input from a user 205 or from a retailer or provider ofgoods or services (e.g. 225). Thus, the user 205 may provide a touch orother input on the mobile device 201 indicating that a payment is to beinitiated. Alternatively, the mobile device 201 may receive anindication from the retailer's point of sale system 206 indicating thata payment transaction has been initiated. In such cases, the inputindicating that the user has initiated a payment for items sold by theprovider of goods or services (i.e. the retailer) is generated by amobile wallet application 210 running on the mobile computer system 201.

The mobile computer system 201 then determines, in Method 300, that theuser and/or the provider has specified preferences indicating whichdebit network is to be used to process the payment (320). As shown inFIG. 2, the user may specify their debit network preferences in userpayment preferences 212. The retailer or goods provider may specifytheir debit network preferences 214 and send them to the user's mobiledevice 201. The retailer's preferences may be sent with the indicationthat a payment has been initiated, or may be sent at another time. Theuser's or the retailer's preferences may be different for each user andfor each retailer. Thus, a user may use different debit networks atdifferent retail locations (e.g. 225), and the retailer may usedifferent debit networks for different users, depending on thesituation. Most commonly, however, the retailer (and likely the user)will prefer a single debit network for all of their debit transactions.

Method 300 next generates a QR code with the debit network selection andone or more portions of the user's debit account information embedded inthe QR code (330). The QR code 221 thus includes information indicatingwhich debit network will be used to process the transaction, and furtherincludes the user's debit account information (e.g. account number,routing number, etc.). In some embodiments, as shown in FIG. 5, the QRcode 501 may include many different portions of embedded information502. While elements 503-509 are all shown as being part of embeddedinformation 502, it will be understood that the QR code and theinformation embedded therein may include any one or more of the itemsshown (i.e. elements 503-509), or may include other items (not shown).As such, the embedded information 502 may be expanded to include anyinformation necessary or helpful in conducting a debit transaction.

Accordingly, the embedded information may include an indication of theuser's preferred debit network 503, an indication of the retailer orprovider's preferred debit network 504, an indication of the totalpayment amount 505 that is to be processed in the debit transaction, alisting of the goods or services being purchased 506, the user's debitaccount information including the user's name, account number, routingnumber or other pertinent information, the user's purchase history (atthat retail location or at other locations), and/or an indication ofrewards 509 that are to be provided to the user or retailer for thatparticular selection of debit network. The embedded information mayalso, at least in some cases, include the retailer's encrypted debitaccount information. Indeed, each portion of embedded information may beencrypted so as to be inaccessible to unauthorized parties.

In some embodiments, the QR code may be automatically generated by themobile wallet application 210 running on the mobile computer system 201when the mobile wallet application is used to pay for the items. The QRcode generating module 220 may determine that a payment transaction hasbeen initiated with the retailer, and may generate the QR code 221,including one or more portions of embedded information. The QR code issecure, and tokenized, such that the code is valid for a single use. Thegenerated QR code is then sent to a payment processing system (340).

The payment processing system may be part of the point of sale 226, ormay be a cloud-based payment processing system (e.g. described inFIG. 1) that is configured to receive and process payments. In somecases, the payment processing system may sit between the user/retailerand the debit network. As such, the payment processing system mayreceive the QR code, and route the debit transaction to the proper debitnetwork (e.g. 230A or 230B). Alternatively, the user may send the QRcode to the retailer's point of sale, which then passes the debittransaction to the proper debit network. Still further, the user maysend the QR code directly to the specified debit network, which willthen decrypt the embedded information and process the debit transaction.

As mentioned above, the selection of a particular debit network may bedetermined dynamically for each user, and at each at each provider ofgoods or services. The debit network selection may include accessing theuser's demographic information, the user's payment preferences and/orthe user's purchasing history. During the selection process, thedetermining module 215 of the mobile computer system 201 may determine,based on the user's demographic information, the user's paymentpreferences and/or the user's purchasing history, which debit network isto be used to route the user's payment and account details. Then, basedon this determination, the mobile computer system 201 may indicate theuser's debit network preference 212. In other cases, the mobile computersystem 201 may receive an indication 214 of the provider's preferencefor debit network, and may select the provider's preferred network toprocess the debit transaction. In at least some embodiments, theretailer's preference for debit network may be selected, regardless ofthe user's preferences, effectively allowing the retailer's preferencesto override the user's. In this manner, a debit network may be selectedfor processing a debit transaction.

FIG. 4 illustrates a flowchart of a method 400 for processing a paymentusing a debit network selected according to information embedded in a QRcode. The method 400 will now be described with frequent reference tothe components and data of environment 200 of FIG. 2.

Method 400 includes receiving a QR code with one or more portions ofembedded payment information, where the embedded payment informationincludes a total payment amount that is to be paid by a user, debitaccount information for the user, and/or an indication of which debitnetwork is to be used to process the payment (410). As mentioned above,the embedded payment information 502 (as shown in FIG. 5) may includethe total payment amount 505, debit account information for the user507, and an indication of which debit network is to be used to processthe payment 510, among other items which may be included in the QRcode's embedded information. The QR code 221 may be sent from the user'smobile computer system 201, and may be received at a cloud-based paymentsystem (such as that shown in FIG. 1) or at the retailer's point of sale226. In some cases, the retailer may then forward the QR code on to acloud-based payment system or to the selected debit network (e.g. 230A)Alternatively, the QR code may be sent directly to the selected debitnetwork (e.g. 230B).

Method 400 next includes determining which debit network is to be usedto process the payment based on the indication provided in the embeddedpayment information in the received QR code (420). The determiningmodule 215 of the mobile computer system 201 may determine which debitnetwork to use based on one or more criteria. The debit network may, forexample, be selected based on the location at which the payment isinitiated (e.g. 225). Additionally or alternatively, the debit networkmay be selected based on time of day at which the payment is initiated.Still further, criteria such as cost per debit transaction may be used(by itself, or in combination with the above criteria). The paymentamount and the user's debit account information may then be sent to thedetermined debit network (430). After the debit transaction has beenprocessed, the debit network will send a receipt to the retailer and/orthe user 205. In some embodiments, the user and/or the retailer mayreceive rewards 231 (such as discounts, coupons, loyalty points,vouchers, or other offers) for selecting and using a specific debittransaction network. In such cases, these rewards may be automaticallytransferred to the user's mobile wallet or to the retailer uponcompletion of the debit transaction.

In this manner, methods, systems and computer program products areprovided which select a debit network using a QR code. Embodiments allowusers to purchase items using a mobile wallet that is linked to a debitaccount. Based on the user's purchase history or demographic informationand based on the retailer's preference, the customer may generate a QRcode which specifies the debit network to use when processing thecustomer's debit transaction. The QR code includes account informationas well as the selection of debit network that is to be used to processthe transaction. In this manner, a retailer may specify which debitnetwork is to be used when processing debit transactions.

The concepts and features described herein may be embodied in otherspecific forms without departing from their spirit or descriptivecharacteristics. The described embodiments are to be considered in allrespects only as illustrative and not restrictive. The scope of thedisclosure is, therefore, indicated by the appended claims rather thanby the foregoing description. All changes which come within the meaningand range of equivalency of the claims are to be embraced within theirscope.

We claim:
 1. A computer system comprising the following: one or moreprocessors; system memory; one or more computer-readable storage mediahaving stored thereon computer-executable instructions that, whenexecuted by the one or more processors, cause the computing system toperform a method for processing a payment using a debit network selectedaccording to information embedded in a scannable code, the methodcomprising the following: receiving a scannable code with one or moreportions of embedded payment information, the embedded paymentinformation including at least the following: a total payment amountthat is to be paid by a user, debit account information for the user,and an indication of which debit network is to be used to process thepayment, the debit network comprising a debit payment processing entitythat processes the initiated debit payment, wherein the indication ofwhich debit network to be used includes (1) a user preferred network,(2) a provider preferred network and (3) a selected network, such thatthe scannable code includes all of (1) the user preferred network, (2)the provider preferred network and (3) the selected network, thescannable code also including an identification of rewards to beprovided when the selected network is used and an identification of oneor more goods or services associated with the total payment amount;determining which debit network is to be used to process the paymentbased on the indication provided in the embedded payment information inthe received scannable code; sending the payment amount and the user'sdebit account information to the determined debit network; and receivingan indication that the payment was processed by the determined debitnetwork.
 2. The computer system of claim 1, wherein the scannable codeis received from the user's mobile computer system.
 3. The computersystem of claim 1, wherein the scannable code is received from aretailer's point of sale.
 4. The computer system of claim 1, wherein thedebit network is selected based on the location at which the payment isinitiated.
 5. The computer system of claim 1, wherein the debit networkis selected based on time of day at which the payment is initiated. 6.The computer system of claim 1, wherein the debit network is selectedautomatically based on one or more criteria.
 7. The computer system ofclaim 6, wherein at least one of the criteria comprises cost per debittransaction.
 8. One or more hardware storage device having storedcomputer-executable instructions which are operable by one or moreprocessors of a computer system to cause the computing system to processa payment using a debit network selected according to informationembedded in a scannable code by implementing the following: the computersystem receiving a scannable code with one or more portions of embeddedpayment information, the embedded payment information including at leastthe following: a total payment amount that is to be paid by a user,debit account information for the user, and an indication of which debitnetwork is to be used to process the payment, the debit networkcomprising a debit payment processing entity that processes theinitiated debit payment, wherein the indication of which debit networkto be used includes (1) a user preferred network, (2) a providerpreferred network and (3) a selected network, such that the scannablecode includes all of (1) the user preferred network, (2) the providerpreferred network and (3) the selected network, the scannable code alsoincluding an identification of rewards to be provided when the selectednetwork is used and an identification of one or more goods or servicesassociated with the total payment amount; the computer systemdetermining which debit network is to be used to process the paymentbased on the indication provided in the embedded payment information inthe received scannable code; the computer system sending the paymentamount and the user's debit account information to the determined debitnetwork; and the computer system receiving an indication that thepayment was processed by the determined debit network.
 9. The hardwarestorage device of claim 8, wherein the scannable code is received fromthe user's mobile computer system and is a QR code.
 10. The hardwarestorage device of claim 8, wherein the scannable code is received from aretailer's point of sale and is a QR code.
 11. The hardware storagedevice of claim 8, wherein the debit network is selected based on thelocation at which the payment is initiated.
 12. The hardware storagedevice of claim 8, wherein the debit network is selected based on timeof day at which the payment is initiated.
 13. The hardware storagedevice of claim 8, wherein the debit network is selected automaticallybased on one or more criteria.
 14. The hardware storage device of claim13, wherein at least one of the criteria comprises cost per debittransaction.
 15. A computer-implemented method, which is implemented bya computing system that includes one or more processor and one or morehardware storage device having stored computer-executable instructionswhich are operable by the one or more processors to cause the computingsystem to process a payment using a debit network selected according toinformation embedded in a scannable code, the method comprising: thecomputer system receiving a scannable code with one or more portions ofembedded payment information, the embedded payment information includingat least the following: a total payment amount that is to be paid by auser, debit account information for the user, and an indication of whichdebit network is to be used to process the payment, the debit networkcomprising a debit payment processing entity that processes theinitiated debit payment, wherein the indication of which debit networkto be used includes (1) a user preferred network, (2) a providerpreferred network and (3) a selected network, such that the scannablecode includes all of (1) the user preferred network, (2) the providerpreferred network and (3) the selected network, the scannable code alsoincluding an identification of rewards to be provided when the selectednetwork is used and an identification of one or more goods or servicesassociated with the total payment amount; the computer systemdetermining which debit network is to be used to process the paymentbased on the indication provided in the embedded payment information inthe received scannable code; the computer system sending the paymentamount and the user's debit account information to the determined debitnetwork; and the computer system receiving an indication that thepayment was processed by the determined debit network.
 16. The method ofclaim 15, wherein the scannable code is received from the user's mobilecomputer system and is a QR code.
 17. The method of claim 15, whereinthe scannable code is received from a retailer's point of sale and is aQR code.
 18. The method of claim 15, wherein the debit network isselected based on the location at which the payment is initiated. 19.The method of claim 15, wherein the debit network is selected based ontime of day at which the payment is initiated.
 20. The method of claim15, wherein the debit network is selected automatically based on one ormore criteria.
 21. The method of claim 20, wherein at least one of thecriteria comprises cost per debit transaction.